OpenText Cordys 10.6 documentation : Case Model Properties Interface

Case Model Properties Interface

This topic describes the various fields on the pane.

The Properties - Case Model pane helps in viewing and setting the properties of a Case model.

Table 1. Fields on the Properties - Case Model Pane

 

 

Tab Field Description
General Name Name of the current Case model. This is a mandatory field.
Description Provide a description for the Case model.
Root State Name All the follow-up activities defined in the model, that are not associated to any specific user-defined State, will be considered to be part of this state. This is an editable field and if required, you can modify the default name provided. The state name provided here can be selected by the Inbox users to list the follow-up activities which are not associated to any specific user-defined State.
Priority

When multiple Case models are executed, the Case instances corresponding to these Case models are created. The priority displays the various levels of the Case model, which assumes importance in the run-time. Using the Priority list, you can select the priority level High, Medium or Low and provide the priority of execution.

Note: If the priority is not set, the Case instances will be executed in FIFO (First-In, First-Out) order. During execution, the Case model with High priority will take precedence over the Case models that are set to lower priority levels.

Case Overview Form A Case overview form is an User Interface (UI) that allows you to view the data related to a Case. In the UI, the information related to the Case data is displayed in the Case Inbox and CIM (Case Instance Monitoring).
When a Case overview form is configured for any Case model, all the users working on that Case model will be able to access the Case overview form. Select the required overview form to attach to the Case model.
Also, you can add a New User Interface or External User Interface or add an existing one from the Select a Case Overview Form window. In the Case overview form, use the SOAP API GetCaseData to access the data associated to a Case instance and populate the controls in the Case overview form.
Applicability Service

Often, the case workers or knowledge workers need to take decisions to select the most applicable sub-set from next set of follow-up activities, based on the context and data available for a Case. In such a scenario, it becomes necessary for a case worker to consider all the possible options and exceptions available for executing a task.

The Applicability Service is a feature that helps a case worker to accomplish tasks easily, while considering all the possible options and exceptions, by implementing the required business logic on a Web service. When the Applicability Service feature is selected for the state, it becomes applicable for all the activities within the state. When the activities within the state are executed, based on the work option or exception, Applicability Service is triggered. Refer to Using the Applicability Service in a Case Model for more information on configuration and related usage.

  • Select Business Process or Web Service from the Applicability Service list.
  • Click to browse and select the related business process or Web service.  
    • If Business Process is selected, only the process models that implement the contract shared are displayed. Implementation of such business processes are based on Contract First Development option with the WSDL that is shared. 
    • If Web Service is selected, only the services that implement the WSDL are considered. 
Data Use XML Schema Fragment A data model gives the structure of the information in the Case model. Select the required XML schema fragment for the Case to add a data model to the Case model. By using CreateCase SOAP API, you can trigger the Case model and pass the instance of the data model.
Case Identifiers


A Case identifier is a business attribute which is used to identify or search for a Case in the Inbox. For example, the Customer ID or Order ID can be considered as the business attributes by the case administrator to search for the Case.
Case data acts as the source for configuring the Case identifiers. Click to add a Case identifier and provide the following details:

  • Name - Name of the Case identifier.
  • Type - Select the type of Case identifier: String, Numeric, or Date.

    Case Identifier Type

    Details

    String

    Supports the storage of string values.

    Numeric

    Supports the storage of integer values only.

    Date

    Supports the storage of date in the yyyy-mm-ddThh:mn:ss.ms format; for example: 2012-10-15T05:01:42.951

  • XPath - Provide the XPath expression of the Case identifier.
Duration Business Calendar Business Calendar allows you to associate the timely business activities with the Case model. Select the required Business Calendar from the available list and attach to the Case model. If you wish to continue with the default calendar, that is 24*7, do not provide any changes.
Duration Type
Escalate to

Escalate to allows you to send notifications to the concerned member working on the Case so as to ensure that the Case will be completed at the earliest possible time. Select the member to whom you wish to send the notification from the list mentioned below.

  • Manager of the user
  • User defined by case variable
  • User who created the case

Note: The escalation feature in Case model notifies the receiver. It will not support the re-assignment of a task.

User

To indicate which case worker must work on the Case, select a case worker. This helps to allocate appropriate case workers to work on the Case.

Note: This option is enabled only if User defined by case variable is selected in the Escalate to list.


Case Variables
Case Variables

A Case variable is used as a parameter in a Case model. It has a type and a default value. A Case model can have zero or more variables and collectively define exactly, which parts of the model can be changed. You can create your own Case variables on any Case model by using the Case Variables tab on the Case model properties page. Case variables help case workers to regulate Case execution behavior at run time, by delaying the specification of certain Case element values, till the instance is actually executed. A lot of decisions are made during design time by the case worker, for example; activities, norm times, business calendars and so on. However, some properties have to be decided by the case worker during run time. To facilitate this process, custom Case variables can be defined with default values by the Case designer. They can be set by the case worker only while creating a Case or updating a Case variable Web services during the run time of the Business Process Model.
Click to add a Case variable and provide the following details:

  • Name - Provide a name for the Case variable.
  • Type - Define the Case variable type as any one of the following:
    • Team - Select Team when it is likely that the team which must perform the human task can change during the course of implementation or at run time.
    • User - Select User when it is likely that the user who must perform the human task can change during the course of implementation or at run time.
    • Role - Select Role when it is likely that the user having a specific role to perform the human task can change during the course of implementation or at run time.
    • Worklist - Select Worklist when it is likely that the members of a worklist who must perform the human task can change during the course of implementation or at run time.
    • Distribution Algorithm - Distribution Algorithm or Scheduling algorithm suggests the handling of requests within a queue.
      By default, the Round Robin algorithm is implemented. It ensures that a task is completed by the case workers one after another in a sequential manner. It also assigns time slices to each process in equal portions and in circular order, handling all the processes without priority. So, if a task is not complete in one time slice, it will be executed in the next cycle. However, you may implement your own scheduling algorithm too.
    • Duration - Duration Case variable is used at the activity level to define its own execution time. There can be different Case variables to define duration for different activities. Provide the duration for the completion of all the activities within the Case model in the Set Duration dialog box.
    • String - Any value that can hold alphanumeric content. This can be used to hold the value that is used to instantiate sub-process models.
        • Default Value - Click to select a default value. Based on the selection of Type, the corresponding default dialog box appears. Select the required value as described below:

          Case Variable Type

          Action

          Team

          Select a team from the Select a Team dialog box.

          User

          Select a user from the Select a User dialog box. You can also use Find a User option to quickly find a user.

          Role

          Select a role from the Select a Role dialog box.

          Distribution Algorithm

          Select the required algorithm from the Select a Dispatch Algorithm dialog box.

          Duration

          Provide the duration in Set Duration in days, hours, and minutes as required.

          String Provide the required value from the look up provided.
  • Description - Provide a description for the Case variable.
    This provides more flexibility because the case worker can now make last minute changes, when creating a specific Case, by overriding the default Case properties. For example, case worker can decide that staff-B must work on a certain activity instead of staff-A.
    Note: This tab appears at the Case model view but not for activity view.
Work Assignment Assignee Type

Based on your business requirements, you may have a single case worker, multiple case workers, or teams working on the Case. Therefore, it is important to select an assignee type to clearly indicate who must work on the current Case. Click to add the type of assignment and to add users or teams so that you may assign them the activities of the Case as follows:

  • Team - The users in the specified team who must work on this Case or activity.
  • Role - The set of users with this role who must work on this Case or activity.
  • Worklist - The list of tasks on which the teams are working.
  • User - The specific user. When you select this value, you also need to create or select a Case variable that contains the value of a role, team, or user that specifies the users.
Work Distribution  

Work distribution is a custom algorithm, which you must define to indicate how the work must be distributed among the case workers. Select one of the following work distribution algorithm:

  • Use System Default - The default settings of the system decides the work distribution.
  • Static (decide when creating the case) > Algorithm - Select the algorithm to be used to distribute work amongst the case workers.
  • Dynamic (decide when creating the case) > Case variable to be used - Select the Case variable to be used to distribute work amongst case workers.
Events Event Name Name of the event that you have created. At times, you may want to define your own event types that are specific for the Case model. Once you create the event types, you can use them at several places. You can use an event to describe what can happen when certain situations like receiving a document, creation of a Case, completion of an activity occur. On an activity, you can also specify the event it can raise. You can use an event to trigger a transition between states.
For example, Event Name: OrderApproval.
Click to add an event.
Description A meaningful description of the event created.
Attachments
Note: The access control list (ACL) or permissions (Read, Write, Delete) defined in the Case model property sheet are applicable to all tasks in the respective Case model.
Label Name Name of the attachment definition. The label name associated with a Document Received Event must not contain the space ( ) character.
Supported Document Types Case models invariably have the need to use applicable or supported Case documents. The Supported Document Types displays a list of all the existing document types that new attachment definition supports. Click to select a document from the list that appears in the Select a Mime Type window.
Note: If a required document type is not available in the list, select Any file type.
Read Select the check box to enable the case worker to download the attached document in the Inbox.
Write Select the check box to enable the case worker to download the attachment, modify it, or add a new attachment to the task in the Inbox.
Delete Select the check box to enable the case worker to view the attachment in the Inbox, modify the contents in the attachment, add another attachment, or delete the attachment too.
Annotation Annotation Provide any additional notes or comments on the Case model.

 

 

Related concepts

Case Management

Related tasks

Creating a Case Model
Designing a Case Model
Setting the Properties of a Case Model
Executing a Case Model

Related information

Modeling Cases